System, method and computer program product delivering mobilized data object to mobile device over multiplexed network

ABSTRACT

In accordance with embodiments, there are provided mechanisms and methods for receiving a command to define at least one mobilized object that implements a view for at least one mobile device of data retrieved from an on-demand service. These mechanisms and methods further include generating the mobilized object including the at least one instruction for defining the view for the at least one mobile device, and pushing the mobilized object to the at least one mobile device.

CLAIM OF PRIORITY

This application claim priority to and is a continuation of U.S.application Ser. No. 12/358,017, entitled “SYSTEM, METHOD AND COMPUTERPROGRAM PRODUCT FOR CREATING MOBILE CUSTOM VIEWS FOR TENANTS OF ANON-DEMAND DATABASE SERVICE”, filed Jan. 22, 2009, now U.S. Pat. No.8,156,205, issued Apr. 10, 2012, through U.S. application Ser. No.13/399,991, entitled “SYSTEM, METHOD AND COMPUTER PROGRAM PRODUCT FORCREATING MOBILE CUSTOM VIEWS FOR TENANTS OF AN ON-DEMAND DATABASESERVICE”, filed Feb. 17, 2012. U.S. application Ser. No. 13/399,991 is ais a continuation of U.S. application Ser. No. 12/358,017, which claimsthe benefit of U.S. Provisional Patent Application 61/022,754 entitled“METHOD AND SYSTEM FOR CREATING MOBILE CUSTOM VIEWS WITH FILTERING FORTENANTS OF A MULTI-TENANT ON-DEMAND SERVICE,” by Forsberg et al., filedJan. 22, 2008, and U.S. Provisional Patent Application 61/022,756entitled “METHOD AND SYSTEM FOR CREATING MOBILE CUSTOM VIEWS FOR TENANTSOF A MULTI-TENANT ON-DEMAND SERVICE,” by Forsberg et al., filed Jan. 22,2008, the entire contents of which are incorporated herein by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

The current invention relates generally to on-demand services, and moreparticularly to creating mobile custom views for tenants of suchon-demand services.

BACKGROUND

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches, which in and of themselves may also be inventions.

In conventional database systems, users access their data resources inone logical database. A user of such a conventional system typicallyretrieves data from and stores data on the system using the user's ownsystems. A user system might remotely access one of a plurality ofserver systems that might in turn access the database system. Dataretrieval from the system might include the issuance of a query from theuser system to the database system. The database system might processthe request for information received in the query and send to the usersystem information relevant to the request.

In some cases, the foregoing database frameworks are utilized in thecontext of mobile devices. For example, an administrator may desire tomanage and configure mobile devices for an organization. Furthermore,the administrator may desire define or configure views for one or moremobile devices for the organization. However, defining a view for themobile device at the mobile device may be burdensome and inefficient.

BRIEF SUMMARY

In accordance with embodiments, there are provided mechanisms andmethods for creating mobile custom views for tenants of an on-demanddatabase service. These mechanisms and methods for creating mobilecustom views for tenants of an on-demand database service can enableembodiments to allow tenants to create and push instructions forgenerating user-defined views to mobile devices, etc. The ability ofembodiments to provide such feature may allow tenants to efficiently andeffectively create interfaces for mobile devices.

In an embodiment and by way of example, a method is provided forreceiving a command to define at least one mobilized object thatimplements a view for at least one mobile device of data retrieved froman on-demand service, generating the mobilized object including the atleast one instruction for defining the view for the at least one mobiledevice, and pushing the mobilized object to the at least one mobiledevice.

While the present invention is described with reference to an embodimentin which techniques for creating mobile custom views for tenants of anon-demand database service are implemented in an application serverproviding a front end for a multi-tenant database on-demand service, thepresent invention is not limited to multi-tenant databases or deploymenton application servers. Embodiments may be practiced using otherdatabase architectures, i.e., ORACLE®, DB2® and the like withoutdeparting from the scope of the embodiments claimed.

Any of the above embodiments may be used alone or together with oneanother in any combination. Inventions encompassed within thisspecification may also include embodiments that are only partiallymentioned or alluded to or are not mentioned or alluded to at all inthis brief summary or in the abstract. Although various embodiments ofthe invention may have been motivated by various deficiencies with theprior art, which may be discussed or alluded to in one or more places inthe specification, the embodiments of the invention do not necessarilyaddress any of these deficiencies. In other words, different embodimentsof the invention may address different deficiencies that may bediscussed in the specification. Some embodiments may only partiallyaddress some deficiencies or just one deficiency that may be discussedin the specification, and some embodiments may not address any of thesedeficiencies.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a method for creating mobile custom views for tenants of anon-demand database service, in accordance with one embodiment.

FIG. 2 shows a method for creating mobile custom views with filteringfor tenants of an on-demand database service, in accordance with oneembodiment.

FIG. 3 shows a system for creating mobile custom views, with or withoutfiltering, for tenants of an on-demand database service, in accordancewith one embodiment.

FIG. 4 shows a user interface for creating mobile custom views, with orwithout filtering, for tenants of an on-demand database service, inaccordance with one embodiment.

FIG. 5 shows a user interface for creating and editing mobile view pagesfor a selected mobile object, in accordance with one embodiment.

FIG. 6 shows a method for creating mobile custom views, with or withoutfiltering, for tenants of an on-demand database service, in accordancewith one embodiment.

FIG. 7 illustrates a block diagram of an example of an environmentwherein an on-demand database service might be used.

FIG. 8 illustrates a block diagram of an embodiment of elements of FIG.7 and various possible interconnections between these elements.

DETAILED DESCRIPTION General Overview

Systems and methods are provided for creating mobile custom views fortenants of an on-demand database service.

In some cases, on-demand database services are utilized in the contextof mobile devices. For example, an administrator may desire to manageand configure mobile devices for an organization. Furthermore, theadministrator may desire define or configure views for one or moremobile devices for the organization. However, defining a view for themobile device at the mobile device may be burdensome and inefficient.

Thus, mechanisms and methods are provided herein for creating mobilecustom views for tenants of an on-demand database service and can enableembodiments to allow tenants to create and push instructions forgenerating user-defined views to mobile devices, etc. The ability ofembodiments to provide such feature may allow tenants to efficiently andeffectively create interfaces for mobile devices.

Next, mechanisms and methods for creating mobile custom views fortenants of an on-demand database service.

FIG. 1 shows a method 100 for creating mobile custom views for tenantsof an on-demand database service, in accordance with one embodiment. Asshown, a command to define a view for at least one mobile deviceassociated with at least one tenant of at least one on-demand service isreceived, the command including at least one mobilized object. Seeoperation 102.

In the context of the present description, an on-demand service refersto any service that that is accessible over a network. In oneembodiment, the on-demand service may include an on-demand databaseservice. In this case, an on-demand database service may include anyservice that relies on a database system that is accessible over anetwork.

In one embodiment, the on-demand database service may include amulti-tenant on-demand database service. In the present description,such multi-tenant on-demand database service may include any servicethat relies on a database system that is accessible over a network, inwhich various elements of hardware and software of the database systemmay be shared by one or more customers. For instance, a givenapplication server may simultaneously process requests for a greatnumber of customers, and a given database table may store rows for apotentially much greater number of customers.

Additionally, in the context of the present description, a tenant refersto any user of the on-demand service. For example, in variousembodiments, the tenants may include customers, subscribers, developers,administrators, and any other users of the on-demand service.

In one embodiment, the command to define a view for the at least onemobile device may be received from a user interface. The user interfacemay include any interface capable of being utilized by a user. Forexample, in various embodiments, the user interface may include a webpage, a web browser, an interface provided in an email, an emailtemplate, and/or any other interface capable of being utilized by auser.

Furthermore, a mobilized component refers to any item encapsulating atleast a definition of one or more visual objects and associatedattributes, where the visual objects may be associated with a userinterface. For example, in various embodiments, the component mayinclude tags such as HTML, Javapages, and ASP.Net, etc. Additionally,the component may include markup language as well as parametersdescribing behavior.

As shown further in FIG. 1, at least one instruction is generated fordefining the view for the at least one mobile device, the at least oneinstruction being based at least in part on the at least one mobilizedobject. See operation 104. In one embodiment, the instruction mayinclude at least one controller instruction for a user interfacecontroller on the at least one mobile device.

In this case, the user interface controller may include any controllerfor controlling the user interface and/or accessing a portion ofstorage. Furthermore, the user interface controller may include anylogic to facilitate such control and/or access. For example, the userinterface controller may include logic for displaying a user interfacecorresponding to the view for the mobile device.

In either case, the instruction may be capable of being executed by aprocessor of the mobile device for defining the view of the mobiledevice. Additionally, the mobilized object may include one or morefields. In this case, the instruction may include instructions toretrieve at least one value corresponding to the one or more fields ofthe mobilized object.

For example, the value corresponding to the one or more fields may beretrieved from a portion of storage associated with the tenant. In oneembodiment, the value may be capable of being processed to provide theview of the mobile device. In addition, the view of the mobile devicemay be displayed on the mobile device.

In one embodiment, the command to define the view may include at leastone attribute. The attribute may include any attribute associated withthe component, such as an image attribute (e.g. color, size, etc.), atext attribute (e.g. font, size, etc.), and/or any other attributeassociated with the mobilized component. In this case, a portion ofstorage associated with the tenant may be accessed to retrieve at leastone value of the attribute.

Furthermore, the at least one instruction for defining the view ispushed to the at least one mobile device associated with the at leastone tenant. See operation 106. In other words, the instruction may besent to the mobile device. As an option, the mobile device may executethe instruction utilizing a processor such that the view is defined.

It should be noted that the view for the mobile device may include anyview that may be displayed on a mobile device. For example, in variousembodiments, the view for the mobile device may include a userinterface, a screen display, and/or any other type of view that may bedisplayed.

In one embodiment, the instruction may be stored in a storage locationassociated with the tenant. As an option, the pushing of the instructionto the mobile device may be performed automatically. For example, thepushing of the instruction to the mobile device may be performedautomatically and the pushing may be triggered by the storage of the atleast one instruction in the storage location associated with thetenant.

As another option, the instruction may include at least one uniqueidentifier (e.g. a token etc.). In this case, the unique identifier maybe utilized for validation of the instruction. For example, the mobiledevice may utilize the at least one unique identifier for performing thevalidation. In this way, it may be determined that the instruction is avalid instruction from a valid source.

In some cases, information used to generate the instructions fordefining the view may be filtered. For example, at least one instructionmay be generated to retrieve at least one filtered value for providingthe view for the mobile device, where the filtered value corresponds toat least one field associated with the mobilized object

FIG. 2 shows a method 200 for creating mobile custom views withfiltering for tenants of an on-demand database service, in accordancewith one embodiment. As an option, the present method 200 may beimplemented in the context of the functionality of FIG. 1. Of course,however, the method 200 may be carried out in any desired environment.The aforementioned definitions may apply during the present description.

As shown, a command to define a view for at least one mobile deviceassociated with at least one tenant of at least one on-demand service isreceived, the command including at least one mobilized object. Seeoperation 202.

Additionally, at least one instruction to retrieve at least one filteredvalue is generated, the at least one filtered value corresponding to atleast one field associated with the at least one mobilized object andbeing utilized to define the view for the at least one mobile device.See operation 204. In one embodiment, the filtered set of values mayresult from the application of a filter to an unfiltered set of valuesretrieved from a portion of storage associated with the at lest onetenant.

For example, the mobilized object may include at least one field. Inthis case, the field may include one or more display fields, a sortorder field, a title field, and/or various other fields. Furthermore,the instruction may include instructions to retrieve at least one valuecorresponding to the field of the mobilized object. The values mayinclude any values for the fields, including characters, strings, and/orany other value.

In one embodiment, the value corresponding to the field may be retrievedfrom a portion of storage associated with the tenant. This valuecorresponding to the at least one field may then be filtered. Thus, aresult of the filtering may include the filtered value. As shown furtherin FIG. 2, the at least one instruction may be pushed to the at leastone mobile device associated with the at least one tenant. See operation206.

FIG. 3 shows a system 300 for creating mobile custom views, with orwithout filtering, for tenants of an on-demand database service, inaccordance with one embodiment. As an option, the system 300 may beimplemented in the context of the functionality of FIGS. 1-2. Of course,however, the system 300 may be implemented in any desired environment.Again, the aforementioned definitions may apply during the presentdescription.

As shown, a server 302 of an on-demand database service is provided. Asshown further, a plurality of mobilized objects 304 are stored on theserver 302. The server 302 is accessible by an administrator userinterface 306. The administrator user interface 306 may include any userinterface accessible by a user. In one embodiment, the administratoruser interface 306 may be provided by the on-demand database service.

As shown further, the server 302 is in communication with at least onemobile device 308 over one or more networks 310. The mobile device 308may include a client application 312 and storage for one or moreinstructions 314 sent from the server 302. It should be noted that themobile device 308 may include any mobile device including a handheldcomputer, a mobile phone, a personal digital assistant (PDA), and/or anyother device.

In operation, an administrator may access the server 302 utilizing theadministrator user interface 306 and may push information from theserver 302 to the mobile device 308. In one embodiment, theadministrator user interface 306 may include a custom view feature. Thecustom view feature of the administrator user interface 306 may allowadministrators to create custom list views that are pushed to the one ormore mobile devices 308.

Using the administrator user interface 306, custom views may be definedfor mobile configurations on individual mobile devices or groups ofmobile devices. An administrator may create custom views for eachmobilized object in the mobile configuration. Administrators may create,edit, and delete mobile custom views for any mobile device associatedwith their organization.

Any number of custom views may be created for each mobile object. In oneembodiment, however, a limit may be placed on the number of custom viewsthat may be created per object. For example, in one embodiment, thelimit of custom views that can be created per object may be ten, etc.

Furthermore, the custom views for each mobilized object in the mobileconfiguration may include a variety of view properties. For example, inone embodiment, the mobile custom list views may include a two columndisplay. As an option, the mobile custom list views may be limited to atwo-column display.

In another embodiment, the custom views may be applied to all records ona mobile device. Additionally, as an option, the custom views may beapplied to only records on a mobile device. In these cases,administrators may not have the ability to restrict the custom view toonly certain records.

In another embodiment, custom list views may only use fields that are onthe mobile device in custom list view filters. For example, if a fieldthat is used in a mobile view is excluded from a mobile configuration,administrators may not be able to save that configuration. As an option,administrators may be notified that the field is used in a list view.

In some cases, administrators may locate the list views and redefine thelist views to avoid using the field they wish to exclude. By definingthe list views, administrators are unlikely to need to make many changesto configurations once the list views are configured. In one embodiment,the administrator may have the ability to save the list viewconfiguration with excluded fields and mark the views that are unusablewith an alert symbol. All views that are marked with this alert signalmay be treated as not mobilized. Furthermore, administrators may bepresented with functionality to sort the records in the list.

FIG. 4 shows a user interface 400 for creating mobile custom views, withor without filtering, for tenants of an on-demand database service, inaccordance with one embodiment. As an option, the user interface 400 maybe implemented in the context of the functionality of FIGS. 1-3. Ofcourse, however, the user interface 400 may be implemented in anydesired environment. Additionally, the aforementioned definitions mayapply during the present description.

As shown, the user interface 400 may be displayed to a tenant (e.g. anadministrator, etc.) as a mobile device configuration detail page. Theuser interface 400 may be presented to the tenant on a server side of anon-demand database service.

A mobile custom views related list 402 is provided and may be located atthe bottom of the user interface 400 below an excluded fields relatedlist 404. Furthermore, a drop down menu mobile object pick list 406 maybe provided, as shown at the top of the related list 402. The drop downmenu mobile object pick list 406 may let administrators select an objectview to display.

In one embodiment, an “All Objects” option may be available so thatadministrators can see all their custom views at one time. As an option,the mobilized objects may appear in the drop down menu mobile objectpick list 406 in alphabetical order. As another option, a default viewmay be set such that All Objects option is displayed.

In one embodiment, the custom views in the related list 402 may appearin the order the administrator created them. Furthermore, each objectmay initially have no list views. As an option, a mobile list viewcolumn in the related list 402 may be able to be sorted. In this way,the administrator may then see the views in ascending or descendingalphabetic order by their name. If the administrator is using the AllObjects option, the object column may also be sortable.

In one embodiment, an active flag may be used to indicate whether a viewis active or inactive. Furthermore, as an option, clicking a “New”button 408 may take administrators to another user interface forcreating new mobile view pages for a selected mobilized object.

If the administrator is using the All Objects option, the administratormay first select an object from the drop down menu mobile object picklist 406, and then the “New” button 408 for creating new mobile viewpages for the selected object displays. It should be noted that, in oneembodiment, the list view may show summary fields such as a data setview which may include, a “View Filter” option, a “Columns Visible”option, and an “Order By” option for the list view.

FIG. 5 shows a user interface 500 for creating and editing mobile viewpages for a selected mobile object, in accordance with one embodiment.As an option, the user interface 500 may be implemented in the contextof the functionality of FIGS. 1-4. Of course, however, the userinterface 500 may be implemented in any desired environment. Again, theaforementioned definitions may apply during the present description.

In operation, a tenant (e.g. an administrator, etc.) may utilize theuser interface 500 to enter a mobile device view name. In oneembodiment, the view name may include a character limit restriction(e.g. 30 characters, etc.). This character limit restriction may beutilized such that the view name may be displayed on the mobile device,for example.

As an option, the new view name established by the administrator may beset to active by default. Once the view name is defined, search criteriamay be defined. In this case, the search criteria may be utilized tofilter mobilized objects, fields of mobilized objects, and/or values ofmobilized objects in a list of mobilized objects.

In one embodiment, “OR” filters may be utilized to filter items.Furthermore, “AND” filters may be utilized to filter items. In this way,multiple terms may be used to filter items such that only certain itemsin the list are displayed. In one embodiment, filtering options may bedisplayed on the user interface 500 in a search criteria or filteringoption section 502.

The fields utilized for filtering may include any number of fieldsassociated with the mobilized objects. For example, the fields mayinclude an application ID to match an application record, a title forthe custom view, a first display field (e.g. a first column, etc.), asecond display field (e.g. a second column, etc.), a database name (e.g.an on-demand database contact where the view will operate, etc.), andvarious other fields.

Additionally, the object may include one or more virtual fields. Thesefields may include a default field for the object (e.g. a “Name” field,etc.), a phone field (e.g. the first field of type “phone”), and a datefield (e.g. a due date field for an activity due date, activity due datetime for an activity, etc.), etc.

Table 1 shows a non-exclusive list of operators that may be used forfiltering, in accordance with one embodiment.

TABLE 1 Operator Function = equals > greater than >= greater than orequals < less than <= less than or equals bt between != not equals bbegins with e ends with c contains

In one embodiment, instead of the operators listed in Table 1, threeoperators may be utilized, “equal to,” “after,” and “before.”Furthermore, in the context of filtering, dates may be filtered based onrelative values. For example, one structure of a date value may be(+/−)(interval)(unit). Thus, the date may be specified as a differentialfrom the current date.

Table 2 shows some example values for dates, in accordance with oneembodiment. In this case, the units are represented as “d” for days, “w”for weeks, “q” for quarters, and “y” for years.

TABLE 2 “+0d” today “+1d” tomorrow “−1w” last week “+0w” this week “+1w”next week “−1m” last month “+0m” this month “+1m” next month “−1q” lastquarter “+0q” this quarter “+1q” next quarter “−1y” last year “+0y” thisyear “+1y” next year

As an option, the unit may expand into a relative date range. Forexample, if equal to “+0w” is specified, the date may be expanded to“between Monday and Sunday” inclusive. If less than or equal to “−1w” isspecified, the date may be expanded to “last week or older.”

The filters may include the operand and the parameters to the operand.In one embodiment, many filters may be changed together by other filtersto achieve complex Boolean logic. For example. Table 3 shows a filterconfiguration, in accordance with one embodiment.

TABLE 3 f1-o== f1-1=vMailingState f1-2=CA

In this example, the “f” indicates a filter is being specified.Additionally, the “1” following the “f” is the filter number. In oneembodiment, the filter number may begin at one and increase in order.The “o” parameter is the operator (e.g. from Table 1, etc.). The rest ofthe field values may become the parameters for the operator. In variousembodiments, different operators may have a different number ofparameters. As shown further in Table 3, in one embodiment, field namesmay be prefixed with a “v.”

In one embodiment, various filters may be combined using AND, OR, andNOT operators in complex trees. For example, another filter may be addedusing one of the valid operators for filters. In this case, all of theoperands may be applied to the operator.

Table 4 shows operators for combining filters, in accordance with oneembodiment.

TABLE 4 Operator Function AND AND all operands together OR OR alloperands together NOT logical NOT operator

Once any filtering criteria has been entered, display columns areselected. For example, information to be displayed in each column of thelist may be selected. In one embodiment, two columns may be availablefor mobile views.

Once the display columns are selected, a sort order for the data in themobile list view is defined. In this case, administrators may optionallysort the data in the list view by two fields in either ascending ordescending order. As an option, sort order may be identified by objectfields (e.g. an “o1” and “o2” field, etc.).

In some cases, administrators may want to define the order in which thecustom views and standard views appear in a list on the mobile device(e.g. a drop-down menu pick list, etc.). In one embodiment, in themobile views related list, the views for an object may appear in theorder the administrator defined using a “define view order” button. Ifthe administrator does not define the order, the standard list views mayappear first, and then the custom views may appear in the order theywere created.

As an option, clicking the define view order button when an object isselected in the related list may display an “Edit View Order” page forthe selected object. Using this interface, administrators may bepresented with an option to check a box to alphabetize the list views ina “Views” menu on the mobile device. Furthermore, administrators mayarrange the list views in the proper sequence using the interface.

In one embodiment, both custom views and standard views may be displayedin a “List Views” list box. In some cases, administrators may want theability to disable the standard list views on the mobile device. Forexample, each object may initially have two list views, “All Records”and “My Records,” which may be the standard views. In this case, the AllRecords view may be the default view for the mobile device. Making thestandard views available in the related list may allow administrators tomanage the order of the standard and custom views, and to disable thestandard views, if desired.

In these cases, administrators may see limited information for standardviews on the detail page because standard views may not necessarily beconfigured the same way a custom view may be configured. Furthermore,administrators may disable or enable custom views for the mobile deviceusing an “Edit Mobile View” interface.

FIG. 6 shows a method 600 for creating mobile custom views, with orwithout filtering, for tenants of an on-demand database service, inaccordance with one embodiment. As an option, the present method 600 maybe implemented in the context of the functionality of FIGS. 1-5. Ofcourse, however, the method 600 may be carried out in any desiredenvironment. The aforementioned definitions may apply during the presentdescription.

As shown, an administrator selects a set of mobilized objects to be on amobile device. See operation 602. The selected set of mobilized objectsis then sent to the mobile device. See operation 604.

In this case, an administrator using an interface on a server side of anon-demand database service may select the set of mobilized objectsutilizing an administrator accessible interface. Upon selection, theadministrator may store the selected set of mobilized objects and theobjects may be pushed to the mobile device.

Using the administrator interface, the administrator may then select oneor more objects of the set of objects to generate a view for the mobiledevice. See operation 606. These objects may be indicated to the mobiledevice in the form of instructions such that, upon execution of theinstructions, the view for the mobile device will be displayed on themobile device. In one embodiment, the instructions may be generated at aserver of the on-demand database service. In another embodiment, theinstructions may be generated at the mobile device.

Furthermore, it is determined whether the administrator updates ordeletes any of the objects using the administrator interface. Seeoperation 608. For example, the administrator may update or delete anobject from a storage location associated with a tenant on a server ofthe on-demand database service. Upon update or deletion, the server ofthe on-demand database service may update or delete informationassociated with the object on the mobile device. See operation 610.

System Overview

FIG. 7 illustrates a block diagram of an environment 710 wherein anon-demand database service might be used. As an option, any of thepreviously described embodiments of the foregoing figures may or may notbe implemented in the context of the environment 710. Environment 710may include user systems 712, network 714, system 716, processor system717, application platform 718, network interface 720, tenant datastorage 722, system data storage 724, program code 726, and processspace 728. In other embodiments, environment 710 may not have all of thecomponents listed and/or may have other elements instead of, or inaddition to, those listed above.

Environment 710 is an environment in which an on-demand database serviceexists. User system 712 may be any machine or system that is used by auser to access a database user system. For example, any of user systems712 can be a handheld computing device, a mobile phone, a laptopcomputer, a work station, and/or a network of computing devices. Asillustrated in FIG. 7 (and in more detail in FIG. 8) user systems 712might interact via a network with an on-demand database service, whichis system 716.

An on-demand database service, such as system 716, is a database systemthat is made available to outside users that do not need to necessarilybe concerned with building and/or maintaining the database system, butinstead may be available for their use when the users need the databasesystem (e.g., on the demand of the users). Some on-demand databaseservices may store information from one or more tenants stored intotables of a common database image to form a multi-tenant database system(MTS). Accordingly, “on-demand database service 716” and “system 716”will be used interchangeably herein. A database image may include one ormore database objects. A relational database management system (RDMS) orthe equivalent may execute storage and retrieval of information againstthe database object(s). Application platform 718 may be a framework thatallows the applications of system 716 to run, such as the hardwareand/or software, e.g., the operating system. In an embodiment, on-demanddatabase service 716 may include an application platform 718 thatenables creation, managing and executing one or more applicationsdeveloped by the provider of the on-demand database service, usersaccessing the on-demand database service via user systems 712, or thirdparty application developers accessing the on-demand database servicevia user systems 712.

The users of user systems 712 may differ in their respective capacities,and the capacity of a particular user system 712 might be entirelydetermined by permissions (permission levels) for the current user. Forexample, where a salesperson is using a particular user system 712 tointeract with system 716, that user system has the capacities allottedto that salesperson. However, while an administrator is using that usersystem to interact with system 716, that user system has the capacitiesallotted to that administrator. In systems with a hierarchical rolemodel, users at one permission level may have access to applications,data, and database information accessible by a lower permission leveluser, but may not have access to certain applications, databaseinformation, and data accessible by a user at a higher permission level.Thus, different users will have different capabilities with regard toaccessing and modifying application and database information, dependingon a user's security or permission level.

Network 714 is any network or combination of networks of devices thatcommunicate with one another. For example, network 714 can be any one orany combination of a LAN (local area network), WAN (wide area network),telephone network, wireless network, point-to-point network, starnetwork, token ring network, hub network, or other appropriateconfiguration. As the most common type of computer network in currentuse is a TCP/IP (Transfer Control Protocol and Internet Protocol)network, such as the global internetwork of networks often referred toas the “Internet” with a capital “I,” that network will be used in manyof the examples herein. However, it should be understood that thenetworks that the present invention might use are not so limited,although TCP/IP is a frequently implemented protocol.

User systems 712 might communicate with system 716 using TCP/IP and, ata higher network level, use other common Internet protocols tocommunicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTPis used, user system 712 might include an HTTP client commonly referredto as a “browser” for sending and receiving HTTP messages to and from anHTTP server at system 716. Such an HTTP server might be implemented asthe sole network interface between system 716 and network 714, but othertechniques might be used as well or instead. In some implementations,the interface between system 716 and network 714 includes load sharingfunctionality, such as round-robin HTTP request distributors to balanceloads and distribute incoming HTTP requests evenly over a plurality ofservers. At least as for the users that are accessing that server, eachof the plurality of servers has access to the MTS' data; however, otheralternative configurations may be used instead.

In one embodiment, system 716, shown in FIG. 7, implements a web-basedcustomer relationship management (CRM) system. For example, in oneembodiment, system 716 includes application servers configured toimplement and execute CRM software applications as well as providerelated data, code, forms, webpages and other information to and fromuser systems 712 and to store to, and retrieve from, a database systemrelated data, objects, and Webpage content. With a multi-tenant system,data for multiple tenants may be stored in the same physical databaseobject, however, tenant data typically is arranged so that data of onetenant is kept logically separate from that of other tenants so that onetenant does not have access to another tenant's data, unless such datais expressly shared. In certain embodiments, system 716 implementsapplications other than, or in addition to, a CRM application. Forexample, system 716 may provide tenant access to multiple hosted(standard and custom) applications, including a CRM application. User(or third party developer) applications, which may or may not includeCRM, may be supported by the application platform 718, which managescreation, storage of the applications into one or more database objectsand executing of the applications in a virtual machine in the processspace of the system 716.

One arrangement for elements of system 716 is shown in FIG. 8, includinga network interface 720, application platform 718, tenant data storage722 for tenant data 723, system data storage 724 for system dataaccessible to system 716 and possibly multiple tenants, program code 726for implementing various functions of system 716, and a process space728 for executing MTS system processes and tenant-specific processes,such as running applications as part of an application hosting service.Additional processes that may execute on system 716 include databaseindexing processes.

Several elements in the system shown in FIG. 7 include conventional,well-known elements that are explained only briefly here. For example,each user system 712 could include a desktop personal computer,workstation, laptop, PDA, cell phone, or any wireless access protocol(WAP) enabled device or any other computing device capable ofinterfacing directly or indirectly to the Internet or other networkconnection. User system 712 typically runs an HTTP client, e.g., abrowsing program, such as Microsoft's Internet Explorer browser,Netscape's Navigator browser, Opera's browser, or a WAP-enabled browserin the case of a cell phone, PDA or other wireless device, or the like,allowing a user (e.g. subscriber of the multi-tenant database system) ofuser system 712 to access, process and view information, pages andapplications available to it from system 716 over network 714. Each usersystem 712 also typically includes one or more user interface devices,such as a keyboard, a mouse, trackball, touch pad, touch screen, pen orthe like, for interacting with a graphical user interface (GUI) providedby the browser on a display (e.g. a monitor screen, LCD display, etc.)in conjunction with pages, forms, applications and other informationprovided by system 716 or other systems or servers. For example, theuser interface device can be used to access data and applications hostedby system 716, and to perform searches on stored data, and otherwiseallow a user to interact with various GUI pages that may be presented toa user. As discussed above, embodiments are suitable for use with theInternet, which refers to a specific global internetwork of networks.However, it should be understood that other networks can be used insteadof the Internet, such as an intranet, an extranet, a virtual privatenetwork (VPN), a non-TCP/IP based network, any LAN or WAN or the like.

According to one embodiment, each user system 712 and all of itscomponents are operator configurable using applications, such as abrowser, including computer code run using a central processing unitsuch as an Intel Pentium® processor or the like. Similarly, system 716(and additional instances of an MTS, where more than one is present) andall of their components might be operator configurable usingapplication(s) including computer code to run using a central processingunit such as processor system 717 of FIG. 7, which may include an IntelPentium® processor or the like, and/or multiple processor units. Acomputer program product embodiment includes a machine-readable storagemedium (media) having instructions stored thereon/in which can be usedto program a computer to perform any of the processes of the embodimentsdescribed herein. Computer code for operating and configuring system 716to intercommunicate and to process webpages, applications and other dataand media content as described herein are preferably downloaded andstored on a hard disk, but the entire program code, or portions thereof,may also be stored in any other volatile or non-volatile memory mediumor device as is well known, such as a ROM or RAM, or provided on anymedia capable of storing program code, such as any type of rotatingmedia including floppy disks, optical discs, digital versatile disk(DVD), compact disk (CD), microdrive, and magneto-optical disks, andmagnetic or optical cards, nanosystems (including molecular memory ICs),or any type of media or device suitable for storing instructions and/ordata. Additionally, the entire program code, or portions thereof, may betransmitted and downloaded from a software source over a transmissionmedium, e.g., over the Internet, or from another server, as is wellknown, or transmitted over any other conventional network connection asis well known (e.g. extranet, VPN, LAN, etc.) using any communicationmedium and protocols (e.g. TCP/IP, HTTP, HTTPS, Ethernet, etc.) as arewell known. It will also be appreciated that computer code forimplementing embodiments of the present invention can be implemented inany programming language that can be executed on a client system and/orserver or server system such as, for example, C, C++, HTML, any othermarkup language, Java™, JavaScript, ActiveX, any other scriptinglanguage, such as VBScript, and many other programming languages as arewell known may be used. (Java™ is a trademark of Sun Microsystems,Inc.).

According to one embodiment, each system 716 is configured to providewebpages, forms, applications, data and media content to user (client)systems 712 to support the access by user systems 712 as tenants ofsystem 716. As such, system 716 provides security mechanisms to keepeach tenant's data separate unless the data is shared. If more than oneMTS is used, they may be located in close proximity to one another (e.g.in a server farm located in a single building or campus), or they may bedistributed at locations remote from one another (e.g. one or moreservers located in city A and one or more servers located in city B). Asused herein, each MTS could include one or more logically and/orphysically connected servers distributed locally or across one or moregeographic locations. Additionally, the term “server” is meant toinclude a computer system, including processing hardware and processspace(s), and an associated storage system and database application(e.g. OODBMS or RDBMS) as is well known in the art. It should also beunderstood that “server system” and “server” are often usedinterchangeably herein. Similarly, the database object described hereincan be implemented as single databases, a distributed database, acollection of distributed databases, a database with redundant online oroffline backups or other redundancies, etc., and might include adistributed database or storage network and associated processingintelligence.

FIG. 8 also illustrates environment 710. However, in FIG. 8 elements ofsystem 716 and various interconnections in an embodiment are furtherillustrated. FIG. 8 shows that user system 712 may include processorsystem 712A, memory system 712B, input system 712C, and output system712D. FIG. 8 shows network 714 and system 716. FIG. 8 also shows thatsystem 716 may include tenant data storage 722, tenant data 723, systemdata storage 724, system data 725, User Interface (UI) 830, ApplicationProgram Interface (API) 832, PL/SOQL 834, save routines 836, applicationsetup mechanism 838, applications servers 800 ₁-800 _(N), system processspace 802, tenant process spaces 804, tenant management process space810, tenant storage area 812, user storage 814, and application metadata816. In other embodiments, environment 710 may not have the sameelements as those listed above and/or may have other elements insteadof, or in addition to, those listed above.

User system 712, network 714, system 716, tenant data storage 722, andsystem data storage 724 were discussed above in FIG. 7. Regarding usersystem 712, processor system 712A may be any combination of one or moreprocessors. Memory system 712B may be any combination of one or morememory devices, short term, and/or long term memory. Input system 712Cmay be any combination of input devices, such as one or more keyboards,mice, trackballs, scanners, cameras, and/or interfaces to networks.Output system 712D may be any combination of output devices, such as oneor more monitors, printers, and/or interfaces to networks. As shown byFIG. 8, system 716 may include a network interface 720 (of FIG. 7)implemented as a set of HTTP application servers 800, an applicationplatform 718, tenant data storage 722, and system data storage 724. Alsoshown is system process space 802, including individual tenant processspaces 804 and a tenant management process space 810. Each applicationserver 800 may be configured to tenant data storage 722 and the tenantdata 723 therein, and system data storage 724 and the system data 725therein to serve requests of user systems 712. The tenant data 723 mightbe divided into individual tenant storage areas 812, which can be eithera physical arrangement and/or a logical arrangement of data. Within eachtenant storage area 812, user storage 814 and application metadata 816might be similarly allocated for each user. For example, a copy of auser's most recently used (MRU) items might be stored to user storage814. Similarly, a copy of MRU items for an entire organization that is atenant might be stored to tenant storage area 812. A UI 830 provides auser interface and an API 832 provides an application programmerinterface to system 716 resident processes to users and/or developers atuser systems 712. The tenant data and the system data may be stored invarious databases, such as one or more Oracle™ databases.

Application platform 718 includes an application setup mechanism 838that supports application developers' creation and management ofapplications, which may be saved as metadata into tenant data storage722 by save routines 836 for execution by subscribers as one or moretenant process spaces 804 managed by tenant management process 810 forexample. Invocations to such applications may be coded using PL/SOQL 834that provides a programming language style interface extension to API832. A detailed description of some PL/SOQL language embodiments isdiscussed in commonly owned U.S. Provisional Patent Application60/828,192 entitled, “PROGRAMMING LANGUAGE METHOD AND SYSTEM FOREXTENDING APIS TO EXECUTE IN CONJUNCTION WITH DATABASE APIS,” by CraigWeissman, filed Oct. 4, 2006, which is incorporated in its entiretyherein for all purposes. Invocations to applications may be detected byone or more system processes, which manage retrieving applicationmetadata 816 for the subscriber making the invocation and executing themetadata as an application in a virtual machine.

Each application server 800 may be communicably coupled to databasesystems, e.g., having access to system data 725 and tenant data 723, viaa different network connection. For example, one application server 800₁ might be coupled via the network 714 (e.g., the Internet), anotherapplication server 800 _(N-1) might be coupled via a direct networklink, and another application server 800 _(N) might be coupled by yet adifferent network connection. Transfer Control Protocol and InternetProtocol (TCP/IP) are typical protocols for communicating betweenapplication servers 800 and the database system. However, it will beapparent to one skilled in the art that other transport protocols may beused to optimize the system depending on the network interconnect used.

In certain embodiments, each application server 800 is configured tohandle requests for any user associated with any organization that is atenant. Because it is desirable to be able to add and remove applicationservers from the server pool at any time for any reason, there ispreferably no server affinity for a user and/or organization to aspecific application server 800. In one embodiment, therefore, aninterface system implementing a load balancing function (e.g., an F5Big-IP load balancer) is communicably coupled between the applicationservers 800 and the user systems 712 to distribute requests to theapplication servers 800. In one embodiment, the load balancer uses aleast connections algorithm to route user requests to the applicationservers 800. Other examples of load balancing algorithms, such as roundrobin and observed response time, also can be used. For example, incertain embodiments, three consecutive requests from the same user couldhit three different application servers 800, and three requests fromdifferent users could hit the same application server 800. In thismanner, system 716 is multi-tenant, wherein system 716 handles storageof, and access to, different objects, data and applications acrossdisparate users and organizations.

As an example of storage, one tenant might be a company that employs asales force where each salesperson uses system 716 to manage their salesprocess. Thus, a user might maintain contact data, leads data, customerfollow-up data, performance data, goals and progress data, etc., allapplicable to that user's personal sales process (e.g., in tenant datastorage 722). In an example of a MTS arrangement, since all of the dataand the applications to access, view, modify, report, transmit,calculate, etc., can be maintained and accessed by a user system havingnothing more than network access, the user can manage his or her salesefforts and cycles from any of many different user systems. For example,if a salesperson is visiting a customer and the customer has Internetaccess in their lobby, the salesperson can obtain critical updates as tothat customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' dataregardless of the employers of each user, some data might beorganization-wide data shared or accessible by a plurality of users orall of the users for a given organization that is a tenant. Thus, theremight be some data structures managed by system 716 that are allocatedat the tenant level while other data structures might be managed at theuser level. Because an MTS might support multiple tenants includingpossible competitors, the MTS should have security protocols that keepdata, applications, and application use separate. Also, because manytenants may opt for access to an MTS rather than maintain their ownsystem, redundancy, up-time, and backup are additional functions thatmay be implemented in the MTS. In addition to user-specific data andtenant-specific data, system 716 might also maintain system level datausable by multiple tenants or other data. Such system level data mightinclude industry reports, news, postings, and the like that are sharableamong tenants.

In certain embodiments, user systems 712 (which may be client systems)communicate with application servers 800 to request and updatesystem-level and tenant-level data from system 716 that may requiresending one or more queries to tenant data storage 722 and/or systemdata storage 724. System 716 (e.g., an application server 800 in system716) automatically generates one or more SQL statements (e.g., one ormore SQL queries) that are designed to access the desired information.System data storage 724 may generate query plans to access the requesteddata from the database.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefinedcategories. A “table” is one representation of a data object, and may beused herein to simplify the conceptual description of objects and customobjects according to the present invention. It should be understood that“table” and “object” may be used interchangeably herein. Each tablegenerally contains one or more data categories logically arranged ascolumns or fields in a viewable schema. Each row or record of a tablecontains an instance of data for each category defined by the fields.For example, a CRM database may include a table that describes acustomer with fields for basic contact information such as name,address, phone number, fax number, etc. Another table might describe apurchase order, including fields for information such as customer,product, sale price, date, etc. In some multi-tenant database systems,standard entity tables might be provided for use by all tenants. For CRMdatabase applications, such standard entities might include tables forAccount, Contact, Lead, and Opportunity data, each containingpre-defined fields. It should be understood that the word “entity” mayalso be used interchangeably herein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to createand store custom objects, or they may be allowed to customize standardentities or objects, for example by creating custom fields for standardobjects, including custom index fields. U.S. patent application Ser. No.10/817,161, filed Apr. 2, 2004, entitled “CUSTOM ENTITIES AND FIELDS INA MULTI-TENANT DATABASE SYSTEM,” which is hereby incorporated herein byreference, teaches systems and methods for creating custom objects aswell as customizing standard objects in a multi-tenant database system.In certain embodiments, for example, all custom entity data rows arestored in a single multi-tenant physical table, which may containmultiple logical tables per organization. It is transparent to customersthat their multiple “tables” are in fact stored in one large table orthat their data may be stored in the same table as the data of othercustomers.

It should be noted that any of the different embodiments describedherein may or may not be equipped with any one or more of the featuresset forth in one or more of the following published applications:US2003/0233404, titled “OFFLINE SIMULATION OF ONLINE SESSION BETWEENCLIENT AND SERVER,” filed Nov. 4, 2002; US2004/0210909, titled “JAVAOBJECT CACHE SERVER FOR DATABASES,” filed Apr. 17, 2003, now issued U.S.Pat. No. 7,209,929; US2005/0065925, titled “QUERY OPTIMIZATION IN AMULTI-TENANT DATABASE SYSTEM,” filed Sep. 23, 2003; US2005/0223022,titled “CUSTOM ENTITIES AND FIELDS IN A MULTI-TENANT DATABASE SYSTEM,”filed Apr. 2, 2004; US2005/0283478, titled “SOAP-BASED WEB SERVICES IN AMULTI-TENANT DATABASE SYSTEM,” filed Jun. 16, 2004; US2006/0206834,titled “SYSTEMS AND METHODS FOR IMPLEMENTING MULTI-APPLICATION TABS ANDTAB SETS,” filed Mar. 8, 2005; and/or US2008/0010243, titled “METHOD ANDSYSTEM FOR PUSHING DATA TO A PLURALITY OF DEVICES IN AN ON-DEMANDSERVICE ENVIRONMENT,” filed Jun. 1, 2007; which are each incorporatedherein by reference in their entirety for all purposes.

While the invention has been described by way of example and in terms ofthe specific embodiments, it is to be understood that the invention isnot limited to the disclosed embodiments. To the contrary, it isintended to cover various modifications and similar arrangements aswould be apparent to those skilled in the art. Therefore, the scope ofthe appended claims should be accorded the broadest interpretation so asto encompass all such modifications and similar arrangements.

1-2. (canceled)
 3. A method of identifying and providing a customizedmobilized component to a mobile device or tablet, the method comprising:receiving a specific application from an application developer, thespecific application including an application programming interface(API) configured to receive the customized mobilized component;receiving a request from the mobile device or tablet for the specificapplication; providing the specific application to the mobile device ortablet in response to receiving the request from the mobile device ortablet; receiving a request for the customized mobilized component asresult of the specific application being executed on the mobile deviceor tablet, the request for the customized mobilized component includingone or more values used to select the customized mobilized component;selecting, from among a plurality of customized mobilized components, acustomized mobilized component that corresponds the one or more valuesaccompanying the request for the customized mobilized component; andtransmitting, for display on the mobile device or tablet, the selectedcustomized mobilized component.
 4. The method of claim 3, wherein theselecting of the customized mobilized component uses (i) the one or morevalues included in the received request for the customized mobilizedcomponent and (ii) values of one or more fields associated with thecustomized mobilized component, to select the customized mobilizedcomponent.
 5. The method of claim 4, wherein the one or more valuesincluded in the received request for the customized mobilized componentincludes a value that identifies a particular account holder whose datais stored in an on-demand database, and wherein the selecting of thecustomized mobilized component further uses data from the on-demanddatabase for the particular account holder identified by the one or morevalues, to select the customized mobilized component.
 6. The method ofclaim 5, wherein the on-demand database includes geographicalinformation of the particular account holder, and wherein the selectingof the customized mobilized component further uses the geographicalinformation of the particular account holder to select the customizedmobilized component.
 7. The method of claim 5, wherein the on-demanddatabase is utilized by an on-demand service for providing thecustomized mobilized component.
 8. The method of claim 4, wherein theone or more values included in the received request for the customizedmobilized component includes a value that identifies a particular userof the mobile device or tablet, wherein the value that identified theparticular user of the mobile device is linked to related informationabout the particular user and that is stored in an on-demand database,and wherein the selecting of the customized mobilized component furtheruses the related information about the particular user to select thecustomized mobilized component.
 9. The method of claim 8, wherein theon-demand database includes geographical information of the particularuser, and wherein the selecting of the customized mobilized componentfurther uses the geographical information of the particular user toselect the customized mobilized component.
 10. The method of claim 8,wherein the on-demand database is utilized by an on-demand service forproviding the customized mobilized component.
 11. The method of claim 4,wherein the one or more values included in the received request for thecustomized mobilized component includes a value that identifies thespecific application, and wherein the selecting of the customizedmobilized component further uses the value that identifies the specificapplication to select the customized mobilized component.
 12. The methodof claim 4, wherein the one or more values included in the receivedrequest for the customized mobilized component includes a value thatidentifies a particular screen size of the mobile device or tablet, andwherein the selecting of the customized mobilized component further usesthe value that identified the particular screen size to select thecustomized mobilized component.
 13. The method of claim 4, wherein theone or more values included in the received request for the customizedmobilized component includes a value that identifies a type of mobilizedcomponent, and wherein the selecting of the customized mobilizedcomponent further uses the value that identifies the type of mobilizedcomponent to select the customized mobilized component.
 14. The methodof claim 4, wherein the one or more values included in the receivedrequest for the customized mobilized component includes a value thatrepresents information related to the mobile device or tablet, andwherein the selecting of the customized mobilized component further usesthe information related to the mobile device or tablet to select thecustomized mobilized component.
 15. The method of claim 3, wherein thecustomized mobilized component includes media content.
 16. Anon-transitory computer readable storage medium impressed with computerprogram instructions to identify and provide a customized mobilizedcomponent to a mobile device or tablet, the instructions, when executedon a processor, implement a method comprising: receiving a specificapplication from an application developer, the specific applicationincluding an application programming interface (API) configured toreceive the customized mobilized component; receiving a request from themobile device or tablet for the specific application; providing thespecific application to the mobile device or tablet in response toreceiving the request from the mobile device or tablet; receiving arequest for the customized mobilized component as result of the specificapplication being executed on the mobile device or tablet, the requestfor the customized mobilized component including one or more values usedto select the customized mobilized component; selecting, from among aplurality of customized mobilized components, a customized mobilizedcomponent that corresponds the one or more values accompanying therequest for the customized mobilized component; and transmitting, fordisplay on the mobile device or tablet, the selected customizedmobilized component.
 17. The non-transitory computer readable storagemedium of claim 16, wherein the selecting of the customized mobilizedcomponent uses (i) the one or more values included in the receivedrequest for the customized mobilized component and (ii) values of one ormore fields associated with the customized mobilized component, toselect the customized mobilized component.
 18. The non-transitorycomputer readable storage medium of claim 16, wherein the one or morevalues included in the received request for the customized mobilizedcomponent includes a value that identifies a particular account holderwhose data is stored in an on-demand database, and wherein the selectingof the customized mobilized component further uses data from theon-demand database for the particular account holder identified by theone or more values, to select the customized mobilized component.
 19. Asystem including one or more processors coupled to a memory, the memoryloaded with computer instructions to identify and provide a customizedmobilized component to a mobile device or tablet, the instructions, whenexecuted on the processors, implement actions comprising: receiving aspecific application from an application developer, the specificapplication including an application programming interface (API)configured to receive the customized mobilized component; receiving arequest from the mobile device or tablet for the specific application;providing the specific application to the mobile device or tablet inresponse to receiving the request from the mobile device or tablet;receiving a request for the customized mobilized component as result ofthe specific application being executed on the mobile device or tablet,the request for the customized mobilized component including one or morevalues used to select the customized mobilized component; selecting,from among a plurality of customized mobilized components, a customizedmobilized component that corresponds the one or more values accompanyingthe request for the customized mobilized component; and transmitting,for display on the mobile device or tablet, the selected customizedmobilized component.
 20. The system claim 19, wherein the selecting ofthe customized mobilized component uses (i) the one or more valuesincluded in the received request for the customized mobilized componentand (ii) values of one or more fields associated with the customizedmobilized component, to select the customized mobilized component. 21.The system of claim 19, wherein the one or more values included in thereceived request for the customized mobilized component includes a valuethat identifies a particular account holder whose data is stored in anon-demand database, and wherein the selecting of the customizedmobilized component further uses data from the on-demand database forthe particular account holder identified by the one or more values, toselect the customized mobilized component.
 22. A method of a mobiledevice or a tablet receiving a customized mobilized component, themethod comprising: transmitting, to an application server, a request fora specific application; receiving the specific application from theapplication server, the specific application including an applicationprogramming interface (API) configured to request the customizedmobilized component; executing the specific application and transmittinga request for the customized mobilized component as result of thespecific application being executed, the request for the customizedmobilized component including one or more values for selecting thecustomized mobilized component; receiving the customized mobilizedcomponent having been selected, from among a plurality of customizedmobilized components, to correspond to the one or more valuesaccompanying the request for the customized mobilized component; anddisplaying the received customized mobilized component.